Skip to content

Conversation

Pakisan
Copy link
Member

@Pakisan Pakisan commented Feb 27, 2025

  • application/raml+yaml;version=1.0
  • application/vnd.google.protobuf;version=2
  • application/vnd.google.protobuf;version=3
  • application/xml

Closes asyncapi/jasyncapi#214

Let's left them like ref, string or object. Generally idk which schema will represent them correctly

- application/raml+yaml;version=1.0
- application/vnd.google.protobuf;version=2
- application/vnd.google.protobuf;version=3
- application/xml
@sonarqubecloud
Copy link

"application/vnd.google.protobuf;version=2",
"application/vnd.google.protobuf;version=3",

"application/xml"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need it here? in the end, it works without it listed here right? in the spec xml is not listed in the list of recommeneded schemas - and also, it is anyway just recommended

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, otherwise here will be error

image

asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  userSignedUp:
    address: user/signedup
    messages:
      UserSignedUp:
        $ref: '#/components/messages/userSignedUp'
operations:
  sendUserSignedUp:
    action: send
    channel:
      $ref: '#/channels/userSignedUp'
    messages:
      - $ref: '#/channels/userSignedUp/messages/UserSignedUp'
components:
  messages:
    userSignedUp:
      payload:
        schemaFormat: application/xml
        schema: |
          <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
            <xs:element name="User">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="displayName" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Name of the user</xs:documentation>
                      </xs:annotation>
                  </xs:element>
                  <xs:element name="email" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>Email of the user</xs:documentation>
                      </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:schema>

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is anyway just recommended

Yep, it's recommendation. But folks from Specmatic already have scenarios where they are using .xsd as payload schema

Without proper registration UI component will not work because of error in our parser

Error thrown during AsyncAPI document parsing. Name: Error, message: Unknown schema format

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Sep 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants